Converting backup copies of objects created using a first backup program to backup copies created using a second backup program

ABSTRACT

Provided are a method, system, and article of manufacture for converting backup copies of objects created using a first backup program to backup copies created using a second backup program. A plurality of backup copies of versions of an object are created using a first backup program, wherein the object has an object name. The first backup program is used to restore at least one of the backup copies to a restored version of the object having a name different from the object name. A second backup program is used to create a backup copy of each restored version of the object. A name of a designated object is assigned to each backup copy created using the second backup program. Metadata of each backup copy created using the second backup program is updated with metadata for the designated object.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.11/845,009, filed on Aug. 24, 2007, which application is incorporatedherein by reference in its entirety.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to a method, system, and article ofmanufacture for converting backup copies of objects created using afirst backup program to backup copies created using a second backupprogram.

2. Description of the Related Art

When creating a backup copy of an object, a vendor backup and recoverysoftware product typically creates a proprietary backup copy that canonly be recovered by the product that created the backup copy. Tomigrate from one backup product to another, the backup copies createdusing the existing product need to be converted to the format of the newproduct.

One technique for converting backup copies created using a currentlydeployed backup program for use with a new backup program involves usingthe current backup program to restore the backup copies for each object,beginning with the oldest, with a new name that varies from the originalobject name from which the backup copies were created using the currentbackup program. The original object is temporarily renamed. For eachrestored backup copy, beginning with the oldest, the restored copy isrenamed to the original name of the object and a backup copy of therestored object is created with the new backup program. The restoredcopy is then deleted. After all the copies have been processed, theoriginal object is renamed back to the original object name. With thisdescribed technique, the original object is unavailable during the timethat the object has the temporary name and the new backup copies arebeing created.

Another technique for converting backup copies created using a currentbackup program for use by a new backup program involves restoring eachbackup copy for an object with a new name, i.e., one that varies fromthe original object name. For each restored backup copy, beginning withthe oldest, a backup copy is created using the new backup program andthe new backup program inventory for that backup copy is updated toindicate that the backup copy is for the original object name as opposedto the temporary name to which the backup copy was restored. Therestored copy is then deleted. During this restore process, themeta-data stored in the internal structure of the backup copy representsthe restored object's temporary name instead of the original name. Thisproblem is typically addressed at the time of restoring the backup copyhaving the temporary object name using the new backup program.

There is a need in the art for improved techniques for converting abackup copy created from a first backup program to a backup copy for usewith a second backup program.

SUMMARY

Provided are a method, system, and article of manufacture for convertingbackup copies of objects created using a first backup program to backupcopies created using a second backup program. A plurality of backupcopies of versions of an object are created using a first backupprogram, wherein the object has an object name. The first backup programis used to restore at least one of the backup copies to a restoredversion of the object having a name different from the object name. Asecond backup program is used to create a backup copy of each restoredversion of the object. A name of a designated object is assigned to eachbackup copy created using the second backup program. Metadata of eachbackup copy created using the second backup program is updated withmetadata for the designated object.

In a further embodiment, the designated object whose name is assigned toeach backup copy created using the second backup program comprises theobject from which the plurality of backup copies were created using thefirst backup program.

In a further embodiment, the object from which the plurality of backupcopies were created using the first backup program comprises a firstobject having a first object name. The designated object whose name isassigned to each backup copy created using the second backup programcomprises a second object having a second object name different from thefirst object name.

In a further embodiment, the metadata of the backup copies created usingthe second backup program is updated with at least one storagemanagement policy indicated in the metadata of the designated object toreplace the at least one storage management policy in the backup copiescreated using the second backup program.

In a further embodiment, the at least one storage management policy is amember of a set of storage management policies comprising an objectexpiration, a migration policy, and a backup policy.

In a further embodiment, the metadata of each backup copy created usingthe second backup program is updated with metadata in the designatedobject indicating an object name of the designated object to replacemetadata in each backup copy created using the second backup programindicating the object name of the backup copy.

In a further embodiment, the metadata of each backup copy created usingthe second backup program is updated with metadata in the designatedobject indicating a directory structure in which the designated objectresides.

In a further embodiment, the metadata of each backup copy created usingthe second backup program is updated with metadata in the designatedobject related to a storage location of the designated object.

In a further embodiment, a backup copy inventory is updated to indicatethat each backup copy created using the second backup program has thename of the designated object.

In a further embodiment, each restored version of the object restoredusing the first backup program is deleted.

In a further embodiment, the first and second backup programs are fromdifferent vendors.

In a further embodiment, users have access to the object during theoperations of using the first backup program to restore each backup copyto the restored version of the object, using the second backup programto create the backup copy of each restored version, assigning the nameof the designated object to each backup copy, and updating the metadataof each backup copy.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an embodiment of a system for converting backupcopies of objects.

FIG. 2 illustrates an embodiment of an entry for a backup copy in abackup copy inventory.

FIG. 3 illustrates an embodiment of object metadata.

FIG. 4 illustrates embodiments of operations to convert backup copies ofobjects created using a first backup program to backup copies createdusing a second backup program.

FIG. 5 illustrates an embodiment of a computer architecture that may beused with the system in FIG. 1.

DETAILED DESCRIPTION

FIG. 1 illustrates an embodiment of a system 2 in communication with astorage 4 having a plurality of objects 6 and backup copies 8 for one ormore of the objects 6. Backup copies 8 for one object 6 comprise backupcopies of versions of the object at different points-in-time. There maybe one or more backup copies 8 for one or more of the objects 6. Thebackup copies 8 may be created using a first backup program 10 or asecond backup program 12. The backup programs 10 and 12 may comprisebackup and restore software from different vendors, different productsfrom a same vendor or different versions of a same product from onevendor.

The first backup program 10 and second backup program 12 maintaininformation on backup copies 8 created using their respective softwarein a first backup copy inventory 14 and a second backup copy inventory16, respectively, which may comprise a database or other informationstore. Object metadata 18 may also be maintained for the objects 6 andbackup copies 8. Object metadata 18 may be included within the internalstructure of the object 6 and backup copy 8 or maintained in a databaseor information store separate from the object 6 or backup copy 8.

A backup copy converter 20 automatically converts backup copies 8created using the first backup program 10 to backup copies 8 createdusing the second backup program 12. A user may use the converter 20 tomigrate backup copies 8 to a different backup program upon changing to anew backup program.

An object 6 may comprise a file system, database object, group of files,or any other data set or grouping of data known in the art that issuitable for backing-up as a backup copy.

The system 2 may comprise a suitable computational device known in theart, such as a server, desktop computer, workstation, mainframe, handheld computing device, telephony device, etc. The storage 4 may beimplemented in a storage system known in the art, such as a storagesystem including a plurality of storage devices, e.g., interconnectedhard disk drives (a Redundant Array of Independent Disks (RAID)), Just aBunch of Disks (JBOD), Direct Access Storage Device (DASD), disksconnected in a loop configuration (serial loop, Fibre Channel ArbitratedLoop), a single storage device, a tape library, an optical library, anetwork attached storage (NAS), etc. The system 2 and storage 4 maycommunicate over a network, direct cable or wireless transmissionmedium.

FIG. 2 illustrates an embodiment of a backup copy inventory entry 50 inthe first 14 and second 16 backup copy inventories. A backup copyinventory entry 50 may include an object identifier (ID) 52 identifyingthe object 6 from which the backup copy was created; a backup copyversion 54 indicating a version of the backup copy, which may be aversion number or timestamp; and a location 56 of the backup copy 8.Additional or different information may also be included in the entry50.

FIG. 3 illustrates an embodiment of object metadata 70 for an object 6and backup copy 8 of an object 6. Object metadata 70 may include anobject identifier (ID) 72 identifying the object 6 or backup copy 8 towhich the metadata applies; storage management policies 74 for theobject 6 or backup copy 8, such as an expiration policy, a migrationpolicy to another storage, and a backup or archival policy; catalogstructure information 76, such as physical location or directorystructure in which the object 6 or backup copy 8 resides; and volumeinformation 78, such as a volume record descriptor, volume table ofcontents and other information on the one or more volumes in which theobject 6 or backup copy 8 resides. The metadata 70 may includeadditional information on the object 6 and backup copy 8.

FIG. 4 illustrates an embodiment of operations performed by the backupcopy converter 20 to convert backup copies 8 created using the firstbackup copy program 10 to backup copies created using the second backupcopy program 12. Upon initiating (at block 100) an operation to convertbackup copies created using the first backup program 10 from a backupobject 6, e.g., backup copies A₁. . . A_(n) created from backup object Awhere n is the number of backup copies, the backup copy converter 20uses, e.g., invokes, (at block 102) the first backup program 10 torestore each backup copy 8 for an object 6 to a restored version of theobject 8 having an object name different from the object name. Forinstance, if the original object is named A and has backup copies A₁. .. A_(n), each restored version may have an object name, e.g., A′different from the original object name A, resulting in restored objectsA′₁. . . A′_(n). The backup copy converter 20 uses (at block 104) thesecond backup program 12 to create a backup copy of each restoredversion of the object. For instance, the second backup program 12 maycreate backup copies of the restored objects A′₁. . . A′_(n), resultingin backup copies A′₁. . . A′_(n).

The backup copy converter 20 assigns (at block 106) a name of adesignated object (comprising the object name from which the restoredbackup copies were generated, e.g., A, or another object name) to eachbackup copy, e.g., backup copies of A′₁. . . A′_(n), created using thesecond backup program 12, resulting in backup copies DN₁. . . DN_(n),wherein “DN” is the designated object name. The designated object namemay comprise the name of the object from which the plurality of backupcopies were created using the first backup program, e.g., A. Forexample, if the initial backup copies were created from object “A”, thenthe backup copies A′₁. . . A′_(n), created using the second backupprogram 12 are assigned the name “A”, resulting in backup copies A₁. . .A_(n) from the second backup program 12. In a further embodiment, thedesignated object name (DN) may be for an object, e.g., object “B”, thatthat is a different name than the object name “A” from which therestored backup copies, e.g., A′₁. . . A′_(n), were created (at block102) using the first backup program 10.

The backup copy converter 20 updates (at block 108) metadata 70 for eachbackup copy created using the second backup program 12, assigned thename of the designated object, e.g., DN₁. . . DN_(n), with metadata 70for the designated object, e.g., storage management policies 74, catalogstructure information 76, and/or volume information 78. In a furtherembodiment, the backup copy object metadata may be updated with anymetadata from the designated object that indicates the name of thedesignated object, so that the metadata 70 for the converted backupcopies, e.g., DN₁. . . DN_(n), is updated to reflect the designatedname, which may comprise the name of the original object, e.g., objectA, from which the backup copies to convert were created, or a differentobject name. In certain situations, if the designated name comprises theoriginal object name, e.g., object A, from which the original backupcopies A₁. . . A_(n), were created, the metadata 70 of the originalobject may have changed following the creation of the original backupcopies, e.g., A₁. . . A_(n). In such case, updating the metadata of thebackup copies A₁. . . A_(n) created using the second backup program 12will capture recently updated metadata from the original object, e.g.,object A.

In one embodiment, the operations at blocks 104-108 may be performed foreach backup object, such that at the time of creating one backup copy ofa restored version of the object, e.g., A′_(i), the designated name,DN_(i), is assigned, and the metadata 70 for the backup copy DN_(i), isstored. In this way, the operations 104-108 are triggered for eachobject so that the operations at blocks 104-108 may be performed for oneobject before being performed for a subsequent object. Alternatively,the operations may be performed for all objects at each block 104-108before proceeding to a subsequent block, such that after all the backupcopies are restored, then all the designated names are assigned, andthen the metadata for the designated named backup copies are updated.

The backup copy converter 20 updates (at block 110) the second backupcopy inventory 16 for the second backup program 12 to indicate that eachbackup copy created using the second backup program 12, e.g., DN₁. . .DN_(n), comprises a backup of the designated object. For instance,updating the second backup copy inventory 16 may involve changing theobject ID 52 in the entries 50 (FIG. 2) for each backup copy DN₁. . .DN_(n), created using the second backup program 12, to the name of thedesignated object. If the object metadata 70 is stored separately fromthe object, then the object ID 72 of the metadata 70 for the backupcopies, DN₁. . . DN_(n), may be updated to indicate the designatedobject name.

The backup copy converter 20 may then delete (at block 112) eachrestored version of the object, e.g., objects A′₁. . . A′_(n), restoredusing the first backup program 10 at block 102 in FIG. 4.

In one embodiment, the backup copy converter 20 may automaticallyconvert all backup copies 8 created using the first backup program 10indicated in the first backup copy inventory 14. Alternatively, thebackup copy converter 20 may automatically convert backup copies 8 forone or more selected objects 6. The designated object name may beprovided by the user of the backup copy converter 20 via a userinterface or command line when invoking the backup copy converter 20.

In one embodiment, the operations of creating the backup copy using thesecond backup program 12, updating the metadata, updating the secondbackup copy inventory 16, and deleting the restored backup copy atblocks 104-112 in FIG. 4 may be performed starting from the oldestbackup copy, e.g., A_(n).

Described embodiments provide operations to convert backup copies of anobject created using a first backup program to backup copies createdusing a second backup program. Further, with certain embodiments, usersmay have continual access to the objects while the backup copies for theobject are being converted because the original object 6 from which thebackup copies were created using the first backup program 10 is notrenamed or otherwise made unavailable during the conversion process.

Additional Embodiment Details

The described operations may be implemented as a method, apparatus orarticle of manufacture using standard programming and/or engineeringtechniques to produce software, firmware, hardware, or any combinationthereof. The described operations may be implemented as code maintainedin a “computer readable medium”, where a processor may read and executethe code from the computer readable medium. A computer readable mediummay comprise media such as magnetic storage medium (e.g., hard diskdrives, floppy disks, tape, etc.), optical storage (CD-ROMs, DVDs,optical disks, etc.), volatile and non-volatile memory devices (e.g.,EEPROMs, ROMs, PROMs, RAMs, DRAMs, SRAMs, Flash Memory, firmware,programmable logic, etc.), etc. The code implementing the describedoperations may further be implemented in hardware logic implemented in ahardware device (e.g., an integrated circuit chip, Programmable GateArray (PGA), Application Specific Integrated Circuit (ASIC), etc.).Still further, the code implementing the described operations may beimplemented in “transmission signals”, where transmission signals maypropagate through space or through a transmission media, such as anoptical fiber, copper wire, etc. The transmission signals in which thecode or logic is encoded may further comprise a wireless signal,satellite transmission, radio waves, infrared signals, Bluetooth, etc.The transmission signals in which the code or logic is encoded iscapable of being transmitted by a transmitting station and received by areceiving station, where the code or logic encoded in the transmissionsignal may be decoded and stored in hardware or a computer readablemedium at the receiving and transmitting stations or devices. An“article of manufacture” comprises computer readable medium, hardwarelogic, and/or transmission signals in which code may be implemented. Adevice in which the code implementing the described embodiments ofoperations is encoded may comprise a computer readable medium orhardware logic. Of course, those skilled in the art will recognize thatmany modifications may be made to this configuration without departingfrom the scope of the present invention, and that the article ofmanufacture may comprise suitable information bearing medium known inthe art.

FIG. 5 illustrates one implementation of a computer architecture 200that may be implemented for the system 2 of FIG. 1. The architecture 200may include a processor 202 (e.g., a microprocessor), a memory 204(e.g., a volatile memory device), and storage 206 (e.g., a non-volatilestorage, such as magnetic disk drives, optical disk drives, a tapedrive, etc.). The storage 206 may comprise an internal storage device oran attached or network accessible storage. Programs, including anoperating system 208, device drivers and application programs, in thestorage 206 are loaded into the memory 204 and executed by the processor202 in a manner known in the art. The architecture further includes anetwork card 210 to enable communication with a network. An input device212 is used to provide user input to the processor 212, and may includea keyboard, mouse, pen-stylus, microphone, touch sensitive displayscreen, or any other activation or input mechanism known in the art. Anoutput device 214 is capable of rendering information transmitted fromthe processor 212, or other component, such as a display monitor,printer, storage, etc.

The terms “an embodiment”, “embodiment”, “embodiments”, “theembodiment”, “the embodiments”, “one or more embodiments”, “someembodiments”, and “one embodiment” mean “one or more (but not all)embodiments of the present invention(s)” unless expressly specifiedotherwise.

The terms “including”, “comprising”, “having” and variations thereofmean “including but not limited to”, unless expressly specifiedotherwise.

The enumerated listing of items does not imply that any or all of theitems are mutually exclusive, unless expressly specified otherwise.

The terms “a”, “an” and “the” mean “one or more”, unless expresslyspecified otherwise.

The variable “n” when used to represent a variable number of an elementmay indicate any number of instances of the element, and may indicatedifferent integer numbers when used with different elements or when usedwith different instances of the same element.

Devices that are in communication with each other need not be incontinuous communication with each other, unless expressly specifiedotherwise. In addition, devices that are in communication with eachother may communicate directly or indirectly through one or moreintermediaries.

A description of an embodiment with several components in communicationwith each other does not imply that all such components are required. Onthe contrary a variety of optional components are described toillustrate the wide variety of possible embodiments of the presentinvention.

Further, although process steps, method steps, algorithms or the likemay be described in a sequential order, such processes, methods andalgorithms may be configured to work in alternate orders. In otherwords, any sequence or order of steps that may be described does notnecessarily indicate a requirement that the steps be performed in thatorder. The steps of processes described herein may be performed in anyorder practical. Further, some steps may be performed simultaneously.

When a single device or article is described herein, it will be readilyapparent that more than one device/article (whether or not theycooperate) may be used in place of a single device/article. Similarly,where more than one device or article is described herein (whether ornot they cooperate), it will be readily apparent that a singledevice/article may be used in place of the more than one device orarticle or a different number of devices/articles may be used instead ofthe shown number of devices or programs. The functionality and/or thefeatures of a device may be alternatively embodied by one or more otherdevices which are not explicitly described as having suchfunctionality/features. Thus, other embodiments of the present inventionneed not include the device itself.

The illustrated operations of FIG. 4 show certain events occurring in acertain order. In alternative embodiments, certain operations may beperformed in a different order, modified or removed. Moreover, steps maybe added to the above described logic and still conform to the describedembodiments. Further, operations described herein may occur sequentiallyor certain operations may be processed in parallel. Yet further,operations may be performed by a single processing unit or bydistributed processing units.

The foregoing description of various embodiments of the invention hasbeen presented for the purposes of illustration and description. It isnot intended to be exhaustive or to limit the invention to the preciseform disclosed. Many modifications and variations are possible in lightof the above teaching. It is intended that the scope of the invention belimited not by this detailed description, but rather by the claimsappended hereto. The above specification, examples and data provide acomplete description of the manufacture and use of the composition ofthe invention. Since many embodiments of the invention can be madewithout departing from the spirit and scope of the invention, theinvention resides in the claims hereinafter appended.

1. A method, comprising: maintaining a plurality of first backup copiesof versions of an object created using a first backup program, whereinthe object has an object name; initiating a backup copy converter set ofoperations to convert the first backup copies created using the firstbackup program to second backup copies created using a second backupprogram by performing: using the first backup program to restore atleast one of the first backup copies to at least one restored version ofthe object having a name different from the object name; using thesecond backup program to create a second backup copy of each of the atleast one restored version of the object; assigning a name of adesignated object to the each second backup copy created using thesecond backup program; and updating metadata of the each second backupcopy created using the second backup program with metadata for thedesignated object.
 2. The method of claim 1, wherein the designatedobject whose name is assigned to the each second backup copy createdusing the second backup program comprises the object from which theplurality of first backup copies were created using the first backupprogram.
 3. The method of claim 1, wherein the object from which theplurality of first backup copies were created using the first backupprogram comprises a first object having a first object name, wherein thedesignated object whose name is assigned to the each second backup copycreated using the second backup program comprises a second object havinga second object name different from the first object name.
 4. The methodof claim 1, wherein the metadata of the each second backup copy createdusing the second backup program is updated with at least one storagemanagement policy indicated in the metadata of the designated object toreplace the at least one storage management policy in the each secondbackup copy created using the second backup program.
 5. The method ofclaim 1, wherein the metadata of the each second backup copy createdusing the second backup program is updated with metadata in thedesignated object indicating an object name of the designated object toreplace metadata in the each second backup copy created using the secondbackup program indicating the object name of the second backup copy. 6.The method of claim 1, wherein the metadata of the each second backupcopy created using the second backup program is updated with metadata inthe designated object indicating a directory structure in which thedesignated object resides.
 7. The method of claim 1, wherein users haveaccess to the object during the operations of using the first backupprogram to restore each first backup copy to the restored version of theobject, using the second backup program to create the second backup copyof each restored version, assigning the name of the designated object tothe each second backup copy, and updating the metadata of the eachsecond backup copy.
 8. A system, comprising: a first backup program; asecond backup program; a storage having objects and a plurality ofbackup copies of versions of an object created using the first backupprogram, wherein the object has an object name; a backup copy converterto convert the first backup copies created using the first backupprogram to second backup copies created using the second backup programby performing operations, the operations comprising: using the firstbackup program to restore at least one of the first backup copies to atleast one restored version of the object having a name different fromthe object name; using the second backup program to create a secondbackup copy of each of the at least one restored version of the object;assigning a name of a designated object to the each second backup copycreated using the second backup program; and updating metadata of theeach second backup copy created using the second backup program withmetadata for the designated object.
 9. The system of claim 8, whereinthe designated object whose name is assigned to the each second backupcopy created using the second backup program comprises the object fromwhich the plurality of first backup copies were created using the firstbackup program.
 10. The system of claim 8, wherein the object from whichthe plurality of first backup copies were created using the first backupprogram comprises a first object having a first object name, wherein thedesignated object whose name is assigned to the each second backup copycreated using the second backup program comprises a second object havinga second object name different from the first object name.
 11. Thesystem of claim 8, wherein the metadata of the second backup copiescreated using the second backup program is updated with at least onestorage management policy indicated in the metadata of the designatedobject to replace the at least one storage management policy in thesecond backup copies created using the second backup program.
 12. Thesystem of claim 8, wherein the metadata of the each second backup copycreated using the second backup program is updated with metadata in thedesignated object indicating an object name of the designated object toreplace metadata in the each second backup copy created using the secondbackup program indicating the object name of the second backup copy. 13.The system of claim 8, wherein the metadata of the each second backupcopy created using the second backup program is updated with metadata inthe designated object indicating a directory structure in which thedesignated object resides.
 14. The system of claim 8, wherein users haveaccess to the object during the operations of using the first backupprogram to restore each first backup copy to the restored version of theobject, using the second backup program to create the second backup copyof each restored version, assigning the name of the designated object tothe each second backup copy, and updating the metadata of the eachsecond backup copy.
 15. An article of manufacture including a backupcopy converter having access to a first backup program and a secondbackup program and a storage, wherein the backup copy converter performsoperations, the operations comprising: determining a plurality of firstbackup copies of versions of an object created using the first backupprogram, wherein the object has an object name; initiating the backupcopy converter to convert the first backup copies created using thefirst backup program to second backup copies created using the secondbackup program by performing: using the first backup program to restoreat least one of the first backup copies to at least one restored versionof the object having a name different from the object name; using thesecond backup program to create a second backup copy of each of the atleast one restored version of the object; assigning a name of adesignated object to the each second backup copy created using thesecond backup program; and updating metadata of each second backup copycreated using the second backup program with metadata for the designatedobject.
 16. The article of manufacture of claim 15, wherein thedesignated object whose name is assigned to the each second backup copycreated using the second backup program comprises the object from whichthe plurality of backup copies were created using the first backupprogram.
 17. The article of manufacture of claim 15, wherein the objectfrom which the plurality of first backup copies were created using thefirst backup program comprises a first object having a first objectname, wherein the designated object whose name is assigned to the eachsecond backup copy created using the second backup program comprises asecond object having a second object name different from the firstobject name.
 18. The article of manufacture of claim 15, wherein themetadata of the second backup copies created using the second backupprogram is updated with at least one storage management policy indicatedin the metadata of the designated object to replace the at least onestorage management policy in the second backup copies created using thesecond backup program.
 19. The article of manufacture of claim 15,wherein the metadata of the each second backup copy created using thesecond backup program is updated with metadata in the designated objectindicating an object name of the designated object to replace metadatain the each second backup copy created using the second backup programindicating the object name of the second backup copy.
 20. The article ofmanufacture of claim 15, wherein the metadata of the each second backupcopy created using the second backup program is updated with metadata inthe designated object indicating a directory structure in which thedesignated object resides.
 21. The article of manufacture of claim 15,wherein users have access to the object during the operations of usingthe first backup program to restore each first backup copy to therestored version of the object, using the second backup program tocreate the second backup copy of each restored version, assigning thename of the designated object to the each second backup copy, andupdating the metadata of the each second backup copy.